Vermin indicates that release is 3.8, and so is this branch.

aaron@Skofnung:~/vcs/obico-server> vermin .
Tips:
- Generic or literal annotations might be in use. If so, try using: --eval-annotations
  But check the caveat section: https://github.com/netromdk/vermin#caveats
- You're using potentially backported modules: argparse, dataclasses, enum, importlib, typing
  If so, try using the following for better results: --backport argparse --backport dataclasses --backport enum --backport importlib --backport typing
- Since '# novm' or '# novermin' weren't used, a speedup can be achieved using: --no-parse-comments
(disable using: --no-tips)

Minimum required versions: 3.8
Incompatible versions:     2
aaron@Skofnung:~/vcs/obico-server> git switch rknn
Switched to branch 'rknn'
Your branch is up to date with 'origin/rknn'.
aaron@Skofnung:~/vcs/obico-server> vermin .
Tips:
- Generic or literal annotations might be in use. If so, try using: --eval-annotations
  But check the caveat section: https://github.com/netromdk/vermin#caveats
- You're using potentially backported modules: argparse, dataclasses, enum, importlib, typing
  If so, try using the following for better results: --backport argparse --backport dataclasses --backport enum --backport importlib --backport typing
- Since '# novm' or '# novermin' weren't used, a speedup can be achieved using: --no-parse-comments
(disable using: --no-tips)

Minimum required versions: 3.8
Incompatible versions:     2

Things to discuss:

• nms_cpu and the post-processing are now used by onnx and rknn, should they be moved into geometry or some other module?
• The RKNN models are target specific, I'm not super happy about just asking the end user to make sure that one is available at build-time...
• The ONNX/Darknet weights are delivered by CDN, should the RKNN ones be done so as well?
• Docker and Podman both require (different!) options to allow the ml_api container to interact with the NPU, which the included docker-composes don't handle. (Do they support inheritance or something like that?)

Of note: this may also address #842, since the RK3588 has the same NPU series. I don't have any boards with that part, I can't confirm.

Oh one thing I should have noticed sooner - the PR needs to use "master" branch as the base. We don't directly merge to the "release" branch.

Can you change the base of this PR to "master"? Thank you!

Oh one thing I should have noticed sooner - the PR needs to use "master" branch as the base. We don't directly merge to the "release" branch.

Can you change the base of this PR to "master"? Thank you!

Rebased to master, I missed it too.

TODO:

• Update docs to indicate that the 'docker-compose' in debian/armbian doesn't support the options used to allow RKNN to read firmware info.
• Add step-by-step for running ml_api or the entire stack on an Radza Zero3 E (the ref board I have been using.

TODO:

• Fix broken checked_call in rknn (looks like args/kwargs not behaving as expected)
  /draft